Remote messaging for mobile communication device and accessory

ABSTRACT

Message notifications to an accessory from a mobile communication device are provided according to some embodiments of the invention. When a message such as a text message, email, and/or voicemail is received at a mobile communication device, the mobile communication device can notify an attached accessory that a message has been received. In response, the accessory can request the full message, media associated with the message, an attachment to the message, and/or an audio/video stream of the message for presentation to a user.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a Continuation of U.S. patent application Ser. No.15/653,432 filed Jul. 18, 2017, which is a Continuation of U.S. patentapplication Ser. No. 14/320,183, filed on Jun. 30, 2014, now issued asU.S. Pat. No. 9,716,986, which is a Continuation of U.S. patentapplication Ser. No. 13/558,217, filed on Jul. 25, 2012, now issued asU.S. Pat. No. 8,798,652, which is a Divisional of U.S. patentapplication Ser. No. 12/479,545, filed on Jun. 5, 2009, now issued asU.S. Pat. No. 8,254,993, which is a Continuation-In-Part of U.S. patentapplication Ser. No. 12/399,740, filed on Mar. 6, 2009, now issued asU.S. Pat. No. 8,140,116, which are incorporated herein by reference intheir entirety and are assigned to the assignee of the presentapplication.

BACKGROUND

The present disclosure relates in general to mobile communicationdevices that interoperate with accessories and in particular tointeroperation of a mobile communication device with an accessory toprovide text message, email and/or voicemail notifications to theaccessory.

Mobile communication devices, such as cellular phones, have becomenearly ubiquitous. Some mobile communication devices, such as theiPhone™ (made by Apple Inc., assignee of the present application), canprovide users a variety of services in addition to mobile telephoneservice; such services can include management and playback of mediacontent (music, videos, audiobooks, photos, etc.); storage of personaldata such as calendar, contacts, and notes; Internet access; and theability to execute various application programs that the user may chooseto download and install.

Some mobile communication devices are designed to interoperate withvarious accessory devices (also referred to herein as accessories). Forexample, a mobile communication device can have a connector with anumber of pins that support providing audio and/or video to anaccessory, receiving audio and/or video from an accessory, providingserial communication to and/or from the accessory, providing power toand/or receiving power from the accessory, and so on. This connector canbe docked or mated with a corresponding connector of an accessory,thereby allowing the exchange of various signals and data between theportable communication device and the accessory.

Accessories can provide a number of different services or serviceenhancements in connection with a mobile communication device. Forexample, some accessories may include speakers to play audio contentreceived from the mobile communication device and/or video displayscreens to display video content, text or other media received from themobile communication device. Some accessories may include a microphoneand may provide audio input from the microphone to the mobilecommunication device, e.g., allowing the mobile communication device toact as a voice recorder. Some accessories may include video and/or stillimage cameras and may provide video and/or image data to the mobilecommunication device for storage and/or playback.

SUMMARY

Certain embodiments of the present invention provide for messagingnotifications—text, email, voicemail, SMS and MMS are all example sothis concept—to an accessory device from a mobile communication device.A mobile communication device in some embodiments can include devicesthat can communicate with a mobile communication network, such as, atelephone network and/or the Internet. The mobile communication devicecan be used to send, receive, display, delete, reply to, forward, and/ortake other actions in response to various types of messages.

Certain embodiments of the present invention provide improvedinteroperability of a mobile communication device with an accessory,including viewing and/or playing text messages, emails, and/orvoicemails. In some embodiments, when a mobile communication device thatis coupled with an accessory (either wired or wirelessly) detectsreceipt of a message (e.g., text message, voicemail and/or email), themobile communication device can notify the accessory. The notification,in some embodiments, can include a portion of the message or the entiremessage. The accessory can notify a user of the mobile communicationdevice's receipt of the message.

In some embodiments, the accessory can request a full message from themobile communication device and present the full message to the user. Insome other embodiments, the accessory can request attachments and/ormedia associated with the message, and present such to the user. In yetother embodiments, voicemails can be streamed from the mobilecommunication device to the accessory for presentation to the user.Various other functions, for example, delete, reply to, callback,forward, etc., can also be supported by the accessory.

The following detailed description together with the accompanyingdrawings will provide a better understanding of the nature andadvantages of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified illustration of a system according to anembodiment of the present invention.

FIG. 2 is a simplified block diagram showing a system according to anembodiment of the present invention.

FIG. 3 is a flow diagram of a process for handling an incoming telephonecall by a mobile communication device according to one embodiment of thepresent invention.

FIG. 4 is a flow diagram of a process for handling an incoming telephonecall by an accessory device according to an embodiment of the presentinvention.

FIG. 5 is a flow diagram of a process for placing a call according to anembodiment of the present invention.

FIG. 6 is a flow diagram of a process for handling a telephone callplaced using an accessory device according to an embodiment of thepresent invention.

FIG. 7 is a message passing diagram illustrating coordination of audioprocessing between a mobile communication device and an accessoryaccording to an embodiment of the present invention.

FIG. 8 is a flow diagram of a process for handing text messages using anaccessory device according to an embodiment of the invention.

FIG. 9 is another flow diagram of a process for handing text messagesusing an accessory device according to an embodiment of the invention.

FIG. 10 is a flow diagram of a process for sending text message to anaccessory from a mobile communication device according to an embodimentof the invention.

FIG. 11 is a flow diagram of a process for handing voicemail using anaccessory device according to an embodiment of the invention.

FIG. 12 is a flow diagram of a process for sending voicemail to anaccessory from a mobile communication device according to an embodimentof the invention.

FIG. 13 shows a flow diagram of a process for an accessory to accessvoicemail through a mobile communication device according to someembodiments.

FIG. 14 shows a flow diagram of a process for allowing an accessory toaccess voicemail through a mobile communication device according to someembodiments.

DETAILED DESCRIPTION

Certain embodiments of the present invention provide improvedinteroperability of a mobile communication device with a speakeraccessory, including echo cancellation. In one embodiment, when a mobilecommunication device that is docked with a speaker accessory detects thebeginning of a phone call (e.g., when a call is received or placed), itcan notify the speaker accessory and disable its own internal echocancellation operations. The speaker accessory, which can also have amicrophone, can enable its echo cancellation operations, providing clearaudio to the parties to the call.

In other embodiments, the coordination of echo cancellation between themobile communication device and the accessory can be applied in phonecalls as well as other situations. For example, a number of situationscan arise where an accessory is receiving audio signals from the mobilecommunication device and concurrently delivering audio signals to themobile communication device, sometimes referred to herein as a “duplex”audio mode. In any such situation, the mobile communication device andthe accessory can coordinate the responsibility for various audioprocessing operations, such as echo cancellation. In one embodiment, themobile communication device can signal to the accessory to indicate whenthe accessory should enter or exit duplex audio mode. When in duplexaudio mode, the accessory can enable its internal audio processingoperations (e.g., echo cancellation) while the mobile communicationdevice disables its corresponding internal operations (or vice versa).When the accessory transitions to a mode other than duplex, the mobilecommunication device can re-enable its own internal audio processingoperations and the accessory can disable its corresponding internaloperations.

In further embodiments, the accessory may provide user input controlsallowing the user to remotely operate the phone functionality of themobile communication device. For example, the accessory may be able toinstruct the mobile communication device to answer or disconnect a call,to place a call to a selected number, to display voice mailnotifications or content, or the like.

In yet further embodiments, an accessory can provide a messaginginterface for a user while coupled with the mobile communication device.For example, the accessory can receive a notification from the mobilecommunication device that a message has been received. The accessory canalert the user with an audible or a visual notification through a userinterface that indicates that the message can be viewed. The message canbe provided to the user through accessory. The message, for example, canbe text, email, voicemail, MMS, SMS, etc.

FIG. 1 is a simplified illustration of a system 100 according to anembodiment of the present invention. System 100 includes a mobilecommunication device 102 that can be connected to an accessory 104 via acable 106. In one embodiment, mobile communication device 102 can be aniPhone™; other mobile communication devices can also be used. Mobilecommunication device 102 can include a built-in speaker 108 and abuilt-in microphone 110. Built-in speaker 108 can produce audible soundin response to a suitable electrical signal, and built-in microphone 110can generate electrical signals in response to incident sound waves.Mobile communication device 102 can also provide a user interface suchas touch-screen display, allowing a user to control mobile communicationdevice 102.

Mobile communication device 102 can support a variety of operationsincluding placing and/or receiving telephone calls, e.g., bycommunicating with a conventional cellular telephone network, othermobile telephone network, or a data network such as the Internet (e.g.,using voice-over-IP technology). During a telephone call, mobilecommunication device 102 can deliver sounds to the user via speaker 108and can receive sounds from the user via microphone 110. Mobile device102 can implement various audio processing operations to optimize thesound quality. For example, mobile communication device 102 can performecho cancellation to reduce feedback between sound produced by speaker108 and sound detected by microphone 110. As another example, mobilecommunication device 102 may also perform noise reduction operationsand/or automatic gain control operations on signals received viamicrophone 110. Those skilled in the art will recognize that a varietyof audio processing techniques, including but not limited to techniquespresently known in the art, can be used in connection with variousembodiments of the present invention; accordingly a detailed descriptionof such techniques has been omitted.

Other operations supported by mobile communication device 102 caninclude, e.g., storage and playback of media assets; access to theInternet, e.g., via wireless connections such as Wi-Fi (referringgenerally to any standard within the IEEE 802.11 family) and/or advancedwireless data networks using third-generation (“3G”) technology; andexecution of various application programs that can be installed onmobile communication device 102 by a user. Some of these applicationprograms may call for mobile communication device 102 to provide audiooutput and/or accept audio input, as well as performing otheroperations, and in some embodiments, mobile communication device 102 canuse built-in speakers 108 and/or microphone 110 whenever audiooperations are needed by a particular application.

Mobile communication device 102 can also include a connector 112 thatcan receive one end connector 113 of cable 106. Connector 112 caninclude a number of pins assigned to carry various signals, includingaudio signals from mobile communication device 102 to accessory 104(referred to herein as “line-out” or “audio-out” signals) and audiosignals from accessory 104 to mobile communication device 102 (referredto herein as “line-in” or “audio-in” signals). Connector 112 can alsoinclude pins assigned to carry other signals, such as video signalsand/or digital data (including, e.g., commands and other information asdescribed below), as well as pins for providing electrical power andground connections between mobile communication device 102 and accessory104. In one embodiment, a certain pin (or pins) can be assigned todeliver power from mobile communication device 102 to accessory 104while another pin (or pins) can be assigned to deliver power fromaccessory 104 to mobile communication device 102. Thus, either device insystem 100 can provide power to the other.

Accessory 104 can receive other end connector 115 of cable 106 at anaccessory connector 114. In some embodiments, accessory connector 114can have a different form factor and/or number of contacts from mobilecommunication device connector 112. In other embodiments, the twoconnectors can be the same, and in still other embodiments, accessoryconnector 114 can be designed to mate directly with mobile communicationdevice connector 112 so that cable 106 is not required. In furtherembodiments, some or all communication between mobile communicationdevice 102 and accessory 104 may take place wirelessly, e.g., viaBluetooth or other short-range wireless protocols.

Accessory 104 can be a speaker dock or any other accessory that iscapable of receiving audio signals from mobile communication device 102and/or providing audio signals to mobile communication device 102 (e.g.,via cable 106). In the embodiment shown, accessory 104 includes stereospeakers 122 that can produce sounds in response to audio signalsreceived from mobile communication device 102 and a microphone 124 thatcan generate electrical signals in response to sounds. Accessory 104 canprovide the electrical signals generated by microphone 124, with orwithout processing, to mobile communication device 102, e.g., via cable106. In particular, accessory 104 may be capable of concurrentlyreceiving audio signals from and supplying audio signals to mobilecommunication device 102; this mode of operation is referred to hereinas “duplex” mode and is contrasted with “simplex” modes in whichaccessory 104 can be either receiving audio signals or supplying audiosignals but not both concurrently.

When operating in duplex mode (or simplex mode), accessory 104 can becapable of performing various audio processing operations to optimizesound quality. For example, when operating in either simplex or duplexmode, accessory 104 can implement noise reduction and/or automatic gaincontrol techniques to improve the quality of signals generated bymicrophone 124. When operating in duplex mode, accessory 104 can alsoimplement echo cancellation techniques between the signals output tospeakers 122 and signals received from microphone 124. As with audioprocessing by mobile communication device 102, a variety of audioprocessing techniques, including but not limited to techniques presentlyknown in the art, can be used in connection with embodiments of thepresent invention; a detailed description of such techniques has beenomitted.

Accessory 104 can also provide user interface components such as volumecontrol 126 and display 128. In addition or instead, accessory 104 canbe equipped with a remote control 130 that can communicate user input toaccessory 104 via a wireless channel (e.g., using infrared orradio-frequency (RF) signaling). Remote control 130 can include variouscontrols, e.g., buttons 132. In some embodiments, remote control 130 caninclude a display area 134 for providing visual information to the user.Thus, a user can operate accessory 104 by interacting directly with userinterface components 126, 128 or by interacting with remote control 130.

In some embodiments, user interface components of accessory 104(including components 126, 128 and/or remote control 130) can beoperated to control various operations of mobile communication device102. For example, accessory 104 can generate commands to mobilecommunication device 102 based on user input received via remote control130; the commands can be communicated to mobile communication device 102via cable 106. Mobile communication device 102 can invoke various of itsfunctions in response to these commands. As one example, a user canoperate remote control 130 (or interface components 126, 128) to placeand/or receive phone calls on mobile communication device 102, asdescribed below.

It will be appreciated that system 100 is illustrative and thatvariations and modifications are possible. A variety of mobilecommunication devices 102 and accessories 104 can be used. The degree towhich mobile communication device 102 can be controlled via accessory104 can be varied as desired.

FIG. 2 is a simplified block diagram showing a system 200 according toan embodiment of the present invention. In some embodiments, system 200can implement system 100 of FIG. 1. System 200 includes a mobilecommunication device (“MCD”) 202 connected to an accessory 204.

MCD 202, which in some embodiments can implement mobile communicationdevice 102 of FIG. 1, includes a processor 206, a user interface 208, astorage device 210, a radio-frequency (“RF”) section 212, an audiosection 214, a video section 216, an accessory I/O (“input/output”)interface 218, a built-in speaker 220 and a built-in microphone (“mic”)222.

Processor 206, which can be implemented as one or more integratedcircuits (including, e.g., a conventional microprocessor ormicrocontroller), can control the operation of MCD 202. For example, inresponse to user input signals provided by user interface 208, processor206 can select and play media assets stored in storage device 210;operate RF section 212 to place and/or receive telephone calls; executevarious application programs residing on storage device 210; and so on.Processor 206 can also manage communication with accessories viaaccessory I/O interface 218.

User interface 208 can include input controls such as a touch pad, touchscreen, scroll wheel, click wheel, dial, button, keypad, or the like, aswell as output devices such as a display screen, indicator lights, etc.,together with supporting electronics (e.g., digital-to-analog oranalog-to-digital converters, signal processors or the like). Althoughshown separately, built-in speaker 220 and/or built-in microphone 222can operate as components of user interface 208 to provide sound outputto a user and to receive sound input from a user, respectively. A usercan operate the various input controls of user interface 208 to invokethe functionality of MCD 202 and can also view and/or hear output fromMCD 202 via user interface 208.

Storage device 210 may be implemented, e.g., using disk, flash memory,or any other non-volatile storage medium. In some embodiments, storagedevice 210 can store media assets such as audio, video, still images, orthe like, that can be played by mobile communication device 202. Storagedevice 210 can also store metadata describing the media assets (e.g.,asset name, artist, title, genre, etc.), playlists (lists of assets thatcan be played sequentially or in random order), and the like. Storagedevice 210 can also store information other than media assets, such asinformation about a user's contacts (names, addresses, phone numbers,etc.); scheduled appointments and events; notes; and/or other personalinformation. In still other embodiments, storage device 210 can storeone or more programs to be executed by processor 206, such as video gameprograms, personal information management programs, programs for playingmedia assets and/or navigating the media asset database, programs forcontrolling a telephone interface to place and/or receive calls, and soon.

RF section 212 provides an interface to a mobile communication network.In one embodiment, the mobile communication network can be a cellulartelephone network or other network capable of carrying a telephone callbetween mobile communication device 102 and another telephone device(not shown). RF section 212 can include analog-to-digital and/ordigital-to-analog circuitry, baseband processing components (e.g.,codecs, channel estimators, and the like), modulators, demodulators,oscillators, amplifiers, transmitters, receivers, transceivers, internaland/or external antennas, and so on. As such, RF section 212 can includeone or more integrated circuits as desired. In some embodiments, someoperations associated with RF section 212 can be implemented entirely orin part as programs executed on processor 206 (e.g., encoding, decoding,and/or other processing in the digital domain), or a dedicated digitalsignal processor can be provided. In some embodiments, RF section 212may also be operable to wirelessly access other communication networkssuch as the Internet, e.g., using 3G, WiFi, Bluetooth, and/or other RFcommunication technologies. Thus, for example, multiple transmitter,receiver, and/or transceiver chips may be present in RF section 212, anddifferent chips may use a separate antenna or share an antenna;alternatively, a single chip can support multiple communication channelsand/or networks using one or more antennas.

Audio section 214 can control the routing of analog and/or digital audiosignals within mobile communication device 202 and can also implementaudio processing operations such as noise reduction, echo cancellation,gain control, analog-to-digital and digital-to-analog conversion, andthe like. (Although shown separately, some or all operations of audiosection 214 can be implemented as software executed by processor 206.)In particular, audio section 214 can select a source to provide inputaudio signals. In one embodiment, audio section 214 can select betweenbuilt-in microphone 222 and a “line-in” signal delivered from accessoryI/O interface 218. In another embodiment, MCD 202 can have one or moreadditional sources of audio signals; for example, MCD 202 may have anexternal microphone jack, a Bluetooth receiver capable of receivingvoice or other audio signals, or the like. Audio section 214 can selectincoming audio from any available source, process the audio as desired(e.g., convert analog audio signals to digital, apply noise reductionand/or echo cancellation, etc.) and route it to another destination. Forinstance, during a phone call, audio section 214 might route incomingaudio from built-in microphone 222 to RF section 212. (A directconnection between audio section 214 and RF section 212 is not shown inFIG. 2, but it is to be understood that such direct routing can beimplemented if desired.)

Similarly, audio section 214 can select a destination to receive outputaudio signals. In one embodiment, audio section 214 can select betweenbuilt-in speaker 220 and a “line-out” signal delivered to accessory I/Ointerface 218. In another embodiment, MCD 202 can have one or moreadditional destinations for output audio signals; for example, MCD 202may have a jack for connecting external speakers or headphones, aBluetooth transmitter capable of transmitting voice or other audiosignals, or the like. Audio section 214 can route audio signals to anyavailable destination. For instance, during a phone call, audio section214 might route incoming audio signals extracted by RF section 212 tobuilt-in speaker 220.

In some embodiments, the routing and processing decisions made by audiosection 214 can be controlled by processor 206. For example, audiosection 214 may have one or more control registers into which processor206 can write control parameters indicating what audio section 214should do. Examples of control parameters include: selection of audiosource; selection of audio destination; selection of which (if any)signal processing operations to perform on a received audio signalbefore routing that signal to a destination; various settings toregulate aspects of audio signal processing operations; and so on. Insome embodiments, program code executing on processor 206 can includeinstructions to update some or all of these control parameters, therebyaltering the manner in which audio is processed and/or routed by audiosection 214.

Video section 216 can control video delivery by MCD 202. For example,during playback of a video asset stored in storage device 210, videosection 216 can route video signals to a built-in display (notexplicitly shown but understood to be part of user interface 208) and/orto a “video out” line of accessory I/O interface 218. In embodimentswhere MCD 202 is capable of receiving video signals from an externalsource, video section 216 can select the external source (e.g., a “videoin” line from accessory I/O interface 218) and direct the video signalsto a destination, for instance, processor 206. Video section 216 in someembodiments can include video processing capability such as imagescaling, format conversions, etc. As with audio section 214, operationof video section 216 can be controlled by processor 206, e.g., bywriting control parameters to control registers of video section 216.

Accessory I/O interface 218 can include a number of signal pathsconfigured to carry various signals between MCD 202 and accessory 204.In one embodiment, accessory I/O interface 218 includes a 30-pinconnector corresponding to the connector used on iPod® and iPhone™products manufactured and sold by Apple Inc. Alternatively oradditionally, accessory I/O interface 218 can include a wirelessinterface (e.g., Bluetooth or the like).

In some embodiments, MCD 202 can also use accessory I/O interface 218 tocommunicate with a host computer (not explicitly shown) that executes amedia asset management program (such as the iTunes® media assetmanagement program distributed by Apple Inc.). In some embodiments, themedia asset management program can allow a user to modify the databaseof media assets stored in storage device 210; to update personal data(e.g., calendar, contacts) stored in storage device 210; and/or to add,update, or remove application programs on storage device 210. In otherembodiments, MCD 202 can include a wireless interface (not explicitlyshown) that can provide communication with a host computer and/or acomputer network.

Accessory 204, which in some embodiments can implement accessory 104 ofFIG. 1, can include a controller 232, a user interface 234, an audiosection 236, an MCD I/O interface 238, a speaker 240, and a microphone242.

Controller 232 can include, e.g., a microprocessor or microcontrollerexecuting program code to perform various functions such as digitalaudio decoding, analog or digital audio and/or video processing,processing of user input, and the like. Controller 232 can also managecommunication with an MCD via MCD I/O interface 238.

User interface 234 can include input controls such as a touch pad, touchscreen, scroll wheel, click wheel, dial, button, keypad, microphone, orthe like, as well as output devices such as a display screen, indicatorlights, etc., together with supporting electronics (e.g.,digital-to-analog or analog-to-digital converters, signal processors orthe like). In some embodiments, user interface 234 can also incorporatea receiver for signals from an associated remote control device (e.g.,remote control 130 of FIG. 1). Although shown separately, speaker 240and/or microphone 242 can operate as components of user interface 234 toprovide sound output to a user and to receive sound input from a user,respectively. A user can operate the various input controls of userinterface 234 to invoke the functionality of accessory 204 and can viewand/or hear output from accessory 204 via user interface 234. In someembodiments, the user can also operate the various input controls ofuser interface 234 to invoke functionality of MCD 202 via accessory 204.For example, in response to user input, controller 232 may generatecommands to be sent to MCD 202 via MCD I/O interface 238.

Audio section 236 can receive the “line-out” signal from MCD 202 via MCDI/O interface 238 and can route the signal appropriately. (Throughoutthis disclosure, the audio signals exchanged between an MCD and anaccessory are referred to from the perspective of the MCD; thus,“line-out” or “audio-out” is to be understood as referring generally toan audio signal delivered from the MCD to the accessory, while “line-in”or “audio-in” refers generally to an audio signal delivered from theaccessory to the MCD.) For instance, audio section 236 can route theline-out signal to speaker 240 or to an external speaker connection (notexplicitly shown). Similarly, audio section 236 can select an audiosignal to be delivered as the “line-in” signal to MCD 202 via MCD I/Ointerface 238. For instance, audio section 236 can select microphone 242or an external microphone connection (not explicitly shown) as an audiosource. In some embodiments, audio section 236 can also effectively cutoff an audio signal; for instance, it can be configured to ignore anyreceived line-out signal from MCD 202 and/or to provide no line-insignal to MCD 202.

In various embodiments, audio section 236 can route signals with orwithout further processing. For example, audio section 236 can beconfigured to perform noise reduction, echo cancellation, gain control,and/or other processing on audio signals received from microphone 242before delivering them to the line-in signal path.

Configuration of audio section 236 can be controlled by controller 232,e.g., by writing control parameter values to control registers of audiosection 236. For example, at a certain time, controller 232 canconfigure audio section 236 to operate in a duplex mode in which aline-out signal received from MCD 202 is routed to speaker 240 (or anexternal speaker connection) concurrently with delivering an audiosignal received from microphone 242 (or an external microphoneconnection) as a line-in signal to MCD 202. At a different time,controller 232 can configure audio section 236 to operate in anoutput-only simplex mode in which line-out is routed to speaker 240while line-in is not generated or in an input-only simplex mode in whichline-in is generated from microphone 242 while line-out is not routed toany destination (i.e., it is ignored).

It will be appreciated that the system configurations and componentsdescribed herein are illustrative and that variations and modificationsare possible. The MCD and/or accessory may have other capabilities notspecifically described herein.

Accessory I/O interface 218 of MCD 202 and MCD I/O interface 238 ofaccessory 204 allow MCD 202 to be connected to accessory 204 andsubsequently disconnected from accessory 204. As used herein, MCD 202and accessory 204 are “connected” whenever a communication channelbetween accessory I/O interface 218 and MCD I/O interface 238 is openand are “disconnected” whenever the communication channel is closed.Connection can be achieved by physical attachment (e.g., betweenrespective mating connectors of MCD 202 and accessory 204), by anindirect connection such as a cable, or by establishing a wirelesscommunication channel. Similarly, disconnection can be achieved byphysical detachment, disconnecting a cable, powering down accessory 204or MCD 202, or closing the wireless communication channel. Thus, avariety of communication channels may be used, including wired channelssuch as USB, FireWire, or universal asynchronous receiver/transmitter(“UART”), or wireless channels such as Bluetooth, WiFi, infrared or thelike. In some embodiments, multiple communication channels between amedia player and an accessory can be open concurrently, or a mediaplayer can be concurrently connected to multiple accessories, with eachaccessory using a different communication channel.

Regardless of the particular communication channel, as long as MCD 202and accessory 204 are connected to each other, the devices cancommunicate by exchanging commands and data according to a protocol. Theprotocol defines a format for sending messages between MCD 202 andaccessory 204. For instance, the protocol may specify that each messageis sent in a packet with a header and an optional payload. The headercan provide basic information such as a start indicator, length of thepacket, and a command to be processed by the recipient, while thepayload provides any data associated with the command; the amount ofassociated data can be different for different commands, and somecommands may provide for variable-length payloads. The packet can alsoinclude error-detection or error-correction codes, e.g., as known in theart. In various embodiments, the protocol can define specific commandsto indicate an action to be taken by the recipient; to signal completionof a task, change of state, or occurrence of an error; and/or toidentify the nature of the associated data. In some embodiments, thecommands may be defined such that any particular command is valid inonly one direction.

The protocol can define a number of “lingoes,” where a “lingo” refersgenerally to a group of related commands that can be supported (orunsupported) by various classes of accessories. In one embodiment, acommand can be uniquely identified by a first byte identifying the lingoto which the command belongs and a second byte identifying theparticular command within the lingo. Other command structures may alsobe used. It is not required that all accessories, or all MCDs to whichan accessory can be connected, support every lingo defined within theprotocol or every command of a particular lingo (for instance, differentdevices might use different versions of a given lingo).

In some embodiments, every accessory 204 and every MCD 202 that aredesigned to be interoperable with each other support at least a“general” lingo that includes commands common to all such devices. Thegeneral lingo can include commands enabling the MCD and the accessory toidentify themselves to each other and to provide at least someinformation about their respective capabilities, including which (ifany) other lingoes each supports and which capabilities of the otherdevice each intends to use while connected. For example, the accessorymay use one or more identification commands to indicate whether it has amicrophone or other source of line-in, whether it can receive line-outfrom MCD 202, whether it supports duplex mode (using both line-in andline-out capabilities of MCD 202 simultaneously), and/or whether itintends to send commands for remotely controlling operations of MCD 202.

The general lingo can also include authentication commands that the MCDcan use to verify the purported identity and capabilities of theaccessory (or vice versa), and the accessory (or MCD) may be blockedfrom invoking certain commands or lingoes if the authentication isunsuccessful.

The protocol can also include various Notify commands that can be sentby MCD 202 to accessory 204 upon the occurrence of certain events. Eachevent may have a different associated Notify command, or fewer Notifycommands can be used, with each instance of a Notify command carryingassociated data indicative of the particular event. In some embodiments,the protocol can also include one or more Register commands thataccessory 204 can use to subscribe to or unsubscribe from receivingparticular Notify commands or notifications of particular events. Inother embodiments, MCD 202 can determine which notifications accessory204 should receive based on the identification information provided byaccessory 204. For instance, if accessory 204 indicates that it canoperate in a duplex mode, MCD 202 may determine that accessory 204should receive notifications as to when duplex mode should be entered orexited. In still other embodiments, a combination of accessory-drivensubscription and determinations by the MCD can be used to control whichnotifications are sent to a particular accessory.

The protocol can also include commands or groups of commands thatsupport remote control of various operations of MCD 202 by accessory204. For example, one remote control command can be a ButtonStatuscommand sendable by accessory 204 to MCD 202. This command can be sentwith associated data in the form of a bitmask indicating the currentstate of various user-operable controls of accessory 204. Based on thebitmask, MCD 202 can take various actions. For example, certain bits ofthe bitmask can be associated with accepting an incoming call(“Answer”), diverting an incoming call to voice mail (“Divert”), orending a current call (“Hang Up”); thus, accessory 204 can instruct MCD202 to take any of these actions.

Another remote control command can be a DialNumber command sendable byaccessory 204 to MCD 202. The associated data for this command can be,for example, a telephone number. Upon receiving this command, MCD 202can initiate a telephone call to the specified number. Still othercommands can be provided. For example, a VoiceDial command sendable byaccessory 204 might be provided. Upon receiving the VoiceDial command,MCD 202 can enable line-in and receive audio from accessory 204. Theuser can then speak a name, telephone number, or other words that map toa particular telephone number into microphone 242; audio section 236routes the corresponding audio signal as line-in to MCD 202. Processor206 (or another component) of MCD 202 can analyze the sound anddetermine a number to call.

Other remote-control commands can be provided to allow a user ofaccessory 204 to navigate contacts stored in storage device 210 of MCD202 by interacting with user interface 234 of accessory 204. Forexample, in one embodiment, the user can search for a contact by name ornumber, or the user can browse a listing of contacts that can befiltered or grouped by name, company name, user-assigned category, orthe like. Such navigation commands can include a selection commandsendable by accessory 204 to inform MCD 202 of the user's desired actionand a responsive command sendable by MCD 202 to provide informationresulting from the action (e.g., a list of contacts or information aboutthe list, such as the number of contacts found) to accessory 204. Insome embodiments, depending on the amount of information sendable by MCD202, a user can view the contact information on a display device ofaccessory 204 and/or on a display device of MCD 202. The navigationalcommands can include a DialContact command sendable by accessory 204 toinstruct MCD 202 to call a contact selected by the user.

It will be appreciated that the protocol described herein isillustrative and that variations and modifications are possible.Specific commands described herein can be replaced with other commandsor combination of commands or other types of messages and formats. Inaddition, it is not required that all of the commands and operationsdescribed herein be supported by any particular mobile communicationdevice or accessory.

Certain embodiments relate to the use of accessory 204 in conjunctionwith MCD 202 to provide a speaker phone, allowing a user to place and/orreceive calls via MCD 202 by operating accessory 204. Referring again toFIG. 2, during a phone call, the user's voice can be detected bymicrophone 242 of accessory 204 and delivered as line-in to MCD 202.Within MCD 202, audio section 214 can route the line-in signal (with orwithout further processing) to RF section 212 to be transmitted acrossthe telephone network, thus allowing the user to speak to the otherparty (or parties) to the call. Similarly, RF section 212 can receivesignals corresponding to the other party's voice. These signals can bedecoded (e.g., in RF section 212 and/or processor 206) and delivered asan audio signal to audio section 214. Audio section 214 can route thissignal (with or without further processing) on the line-out path toaccessory 204. Within accessory 204, audio section 236 can route theline-out signal to speaker 240, thus allowing the user to hear the otherparty. During such operations, built-in speaker 220 and built-inmicrophone 222 of MCD 202 can be disabled.

During such a phone call, echo cancellation between speaker 240 andmicrophone 242 may be desirable to the extent that microphone 242 canpick up sounds from speaker 240. As described above, both MCD 202 andaccessory 204 can have echo cancellation capability; however, it wouldnot be desirable for both to perform echo cancellation on the samesignal. Accordingly, some embodiments provide coordinated control ofecho cancellation so that echo cancellation is performed by only onedevice. In embodiments described below, accessory 204 performs the echocancellation during a phone call; echo cancellation built into accessory204 can be more readily optimized for the particular characteristics ofspeaker 240 and microphone 242. However, other embodiments may providethat MCD 202 performs echo cancellation.

FIG. 3 is a flow diagram of a process 300 for handling an incomingtelephone call by a mobile communication device according to oneembodiment of the present invention. In this embodiment, before the callis received, a mobile communication device (e.g., MCD 202 of FIG. 2) isconnected to an accessory (e.g., accessory 204) that is operable in aduplex mode but not currently operating in duplex mode. For example, theaccessory might be operating as a speaker dock, playing audio contentstored on MCD 202.

Process 300 can start when accessory 204 becomes connected to MCD 202.At block 302, MCD 202 establishes communication with accessory 204. Insome embodiments, establishing communication can include identificationand authentication in accordance with the communication protocol. Atblock 304, MCD 202 can obtain capability information from accessory 204.For example, accessory 204 can indicate whether it provides amicrophone, whether it is capable of operating in a duplex mode, andwhether it provides echo cancellation; accessory 204 can also provideany other applicable information about its capabilities, including otheraudio processing capabilities such as noise reduction. In someembodiments, accessory 204 can provide any or all of its capabilityinformation as part of establishing communication at block 302. In someembodiments, process 300 continues only if accessory 204 supports atleast duplex mode and echo cancellation.

At block 306, MCD 202 can begin delivering audio signals (line-out) toaccessory 204. For example, a user might operate MCD 202, eitherdirectly or using a remote control feature supported by accessory 204,to select one or more audio or video tracks for playback. MCD 202 canroute the audio portion of the track to accessory 204. Delivery of audiosignals to accessory 204 can continue indefinitely.

At block 308, MCD 202 detects a phone call (in this example, an incomingcall) and can generate an alert for the user. For example, MCD 202 canpause the playback of any currently playing track and play a ring tone,display a message, vibrate, and/or take other action to alert a user toan incoming phone call. At block 310, MCD 202 determines whether theuser desires to answer the call. For example, the user can press an“answer” button on MCD 202. Or in some embodiments, the user cancommunicate a desire to answer by operating accessory 204, which cansend a remote-control command such as the ButtonStatus command describedabove to report the user's desire to MCD 202. The user can also choosenot to answer, e.g., by operating a “divert” control to divert the callto voice mail or by taking no action at all within an allotted period.If the user does not answer the call, MCD 202 can resume playback of thecurrently playing track, and process 300 can return to step 306 untilanother incoming call is detected.

If, at block 310, the user chooses to answer the call, then at block312, MCD 202 notifies accessory 204 to enter duplex mode and to enableits echo cancellation features. In one embodiment MCD 202 can send a“begin call” notification message to indicate that a phone call is nowin progress, and accessory 204 can interpret this message as a signal toenter duplex mode and enable echo cancellation. In another embodiment,MCD 202 can send one or more specific commands to instruct accessory 204to enter duplex mode and enable echo cancellation. At block 314, MCD 202can disable its own internal echo cancellation. In some embodiments, ifMCD 202 has not already enabled line-in from accessory 204, it can do soat block 314.

At block 316, MCD 202 can deliver received audio content for the phonecall to accessory 204 as the line-out signal. As described above, thiscontent may be received via RF section 212 and processed (or not) byaudio section 214 prior to delivery as line-out. At block 318, MCD 202can process audio content received from accessory 204 via line-in andtransmit it to the mobile communication network, e.g., via RF section212. Such processing can include conversion to a digital format,modulation, etc., but in this embodiment does not include echocancellation by MCD 202 (which was disabled at block 314). It is to beunderstood that acts associated with blocks 316 and 318 may be performedsimultaneously or concurrently; thus, the user can speak to the callerwhile hearing anything the caller might say.

At block 320, it is determined whether the call should be disconnected.For example, MCD 202 may detect that the call has been terminated by themobile communication network (e.g., if the other party hangs up or theconnection is lost). MCD 202 may also detect that its user has indicatedthat the call should end. For instance, in some embodiments, the usercan press a “hang up” button on MCD 202; in other embodiments, the usercan communicate a desire to end the call by operating accessory 204,which can send a remote-control command such as the ButtonStatus commanddescribed above to report the user's desire to MCD 202. Until such timeas MCD 202 determines that the call should be disconnected, blocks 316and 318 can continue to be executed. Once MCD 202 determines that thecall should be ended, at block 322, MCD 202 can notify accessory 204 ofthe end of the call. In one embodiment, MCD 202 can send an “end call”notification message to indicate that the phone call is no longer inprogress. Accessory 204 can interpret this notification as a signal toexit duplex mode (e.g., returning to the line-out-only mode) and todisable its echo cancellation.

At block 324, MCD 202 can reset its internal state to the statepreceding the phone call, e.g., line-out enabled, line-in disabled.Process 300 can return to block 306; for example, MCD 202 can resumeplaying the track that was paused when the phone call was detected atblock 308. Process 300 can continue indefinitely, e.g., until accessory204 and MCD 202 become disconnected.

FIG. 4 is a flow diagram of a process 400 for handling an incomingtelephone call by an accessory device according to an embodiment of thepresent invention. Process 400 can be executed by accessory 204 whileMCD 202 executes process 300.

Process 400 can start when accessory 204 becomes connected to MCD 202.At block 402, accessory 204 establishes communication with MCD 202. Likeblock 302 of process 300, block 402 can include identification andauthentication in accordance with the communication protocol. At block404, accessory 204 can provide capability information to MCD 202. Forexample, accessory 204 can indicate whether it provides a microphone,whether it is capable of operating in a duplex mode, and whether itprovides echo cancellation; accessory 204 can also provide any otherapplicable information about its capabilities, including other audioprocessing capabilities such as noise reduction. In some embodiments,accessory 204 can provide any or all of its capability information aspart of establishing communication at block 402. In some embodiments,process 400 continues only if accessory 204 supports at least duplexmode and echo cancellation.

At block 406, accessory 204 can initialize its audio state, e.g., inline-out simplex mode. In this mode, accessory 204 can receive line-outfrom MCD 202 (block 408) but does not provide line-in to MCD 202; insome embodiments, audio section 236 of accessory 204 disables sending ofsignals onto the line-in path while in line-out simplex mode. Line-outsimplex mode supports various operations not requiring two-way audio.For example, as noted above, a user can operate MCD 202 (either directlyor using remote-control features supported by accessory 204) to playback various media tracks; the audio portion of the playback can bereceived as line-out by accessory 204. Process 400 can remain at block408 indefinitely.

At block 410, accessory 204 receives a notification from MCD 202 that itshould enter duplex mode and enable its echo cancellation features. Forexample, as described above, the notification can be a “begin call”notification message or one or more specific commands directing theaccessory to take these actions. At block 412, accessory 204 responds tothe notification by enabling its internal echo cancellation and enablingline-in to MCD 202, thus entering duplex mode.

At block 414, accessory 204 can play the line-out signal for the user(e.g., on speaker 240) while concurrently processing audio input (e.g.,from microphone 242) and delivering the processed audio input as line-into MCD 202. In this embodiment, processing of audio input by accessory204 includes the echo cancellation that was enabled at block 412.Process 400 can continue at block 414 for as long as the phone callcontinues.

At block 416, accessory 204 can receive a notification from MCD 202 thatduplex mode should be exited. For example, as described above, thenotification can be an “end call” notification message or one or morecommands instructing the accessory to take specific actions such asexiting duplex mode. At block 418, accessory 204 can respond to thenotification by disabling its internal echo cancellation and disablingline-in to MCD 202, thus resuming the line-out simplex mode. Process 400can then return to block 406. Thus, like process 300, process 400 cancontinue e.g., until accessory 204 and MCD 202 become disconnected.

It will be appreciated that processes 300 and 400 are illustrative andthat variations and modifications are possible. Steps described assequential may be executed in parallel, order of steps may be varied,and steps may be modified, combined, added or omitted. For instance,while the embodiment above describes the accessory as operating in aline-in simplex mode when a call is not in progress, other modes canalso be used. For example, the accessory can operate in a line-outsimplex mode when a call is not in progress, as might be the case if theuser is operating the accessory and mobile communication device torecord voice or other audio input via a microphone. (In such a case, theaccessory's echo cancellation might not be active prior to the phonecall since no signal is being delivered to the accessory's speaker.)Such recording can be paused when a call is received. In some instances,the accessory might have both line-in and line-out disabled at a timewhen a call is not in progress, e.g., if the user is simply using theaccessory to charge the mobile communication device and is neitherlistening to nor recording audio. Where this is the case, the accessorycan respond to a begin-call notification by enabling both line-in andline-out.

Further, the processes described above can be used to manage other typesof audio processing in addition to or instead of echo cancellation. Insome embodiments, for example, both the accessory and the mobilecommunication device can be capable of applying noise reductiontechniques to an audio signal. Often, applying noise reduction at twostages can actually degrade the signal; thus, it may be desired tocoordinate which device performs noise reduction. In one embodiment, thebegin-call notification can signal the accessory to enable noisereduction and/or other audio processing in addition to or instead ofecho cancellation, and the mobile communication device can disable itsinternal noise reduction, echo cancellation, or any other audioprocessing task that is designated to be handled by the accessory duringthe call. In some embodiments, the capability information exchangedbetween the mobile communication device and the accessory can includeinformation indicating which audio processing capabilities the accessorydoes or does not use when in duplex mode. When a call is in progress,the accessory can enable the specified capabilities; when no call is inprogress, these capabilities can be enabled or disabled depending on howthe accessory is being used at any given time.

In addition, the embodiments described above refer to situations inwhich a phone call is received by MCD 202. In other embodiments, anaccessory and a mobile communication device can interoperate to allow auser to place a call. For example, in process 300, detecting a call atstep 308 can also include detecting that the user is placing a call. Insome embodiments, a user can place a call by interacting directly withthe user interface of the mobile communication device even while theaccessory is connected and can then use the accessory to provide audioinput and output for the call as described above.

In other embodiments, a user can place a call by interacting with anaccessory rather than directly with a mobile communication device. FIG.5 is a flow diagram of a process 500 for placing a call according to anembodiment of the present invention. Process 500 can be executed by anaccessory (e.g., accessory 204 of FIG. 2) that is connected to a mobilecommunication device (e.g., MCD 202 of FIG. 2).

Process 500 can start when accessory 204 becomes connected to MCD 202.At block 502, accessory 204 establishes communication with MCD 202. Aswith process 400 described above, block 502 can include identificationand authentication in accordance with the communication protocol. Atblock 504, accessory 204 can provide capability information to MCD 202.In particular, accessory 204 can indicate whether it provides amicrophone, whether it is capable of operating in a duplex mode, whetherit provides echo cancellation, and whether it intends to use remotecontrol commands to control the MCD; accessory 204 can also provide anyother applicable information about its capabilities, including otheraudio processing capabilities such as noise reduction. In someembodiments, accessory 204 can provide any or all of its capabilityinformation as part of establishing communication at block 502. In someembodiments, process 500 continues only if accessory 204 supports duplexmode and echo cancellation and also uses remote control commands.

At block 506, accessory 204 initializes its audio mode, e.g., toline-out simplex mode. In this mode, accessory 204 can receive aline-out signal from MCD 202 (block 508) but does not provide a line-insignal to MCD 202. For example, as noted above, a user can operate MCD202 (either directly or using remote-control features supported byaccessory 204) to play back various media tracks; the audio portion canbe received on the line-out path by accessory 204. Process 500 canremain at block 508 indefinitely. (As noted above, other embodiments mayuse other audio modes such as line-in simplex or audio-off mode.)

At block 510, accessory 204 detects user input requesting initiation ofa phone call. For example, accessory 204 may provide user input controlsthat allow a user to dial a number, and accessory 204 can detect thatthe user has entered a number to dial. In other examples, accessory 204may provide voice dialing, and the user can operate a control toindicate the desire to speak a phone number or name to be called.

At block 512, accessory 204 can send an appropriate phone-dialingcommand to MCD 202. For example, as noted above, the communicationprotocol can include a DialNumber command, allowing accessory 204 toprovide MCD 202 with a number to be dialed. In the case of voicedialing, accessory 204 can enable line-in to MCD 202, disable line-outfrom MCD 202 and send a VoiceDial command to MCD 202; in response to theVoiceDial command, MCD 202 can sample the signal received via line-in todetect and recognize the user's spoken instruction and thereby determinea number to dial.

At block 514, accessory 204 can receive a message from MCD 202indicating whether the call was successfully connected. In oneembodiment, this can include the same begin-call notification as used inprocesses 300 and 400 described above, and the notification can be sentapproximately when MCD 202 begins to place the call. At block 516,accessory 204 can respond to the begin-call notification by enablingecho cancellation and entering duplex mode (e.g., enabling line-in toMCD 202). At block 518, accessory 204 can play line-out signals receivedfrom MCD 202 for the user while processing microphone input anddelivering the processed input via line-in to MCD 202; this can besimilar to block 414 of process 400 described above.

In some embodiments, the accessory can enter duplex audio mode while MCD202 is attempting to place the call. Thus, to the extent that MCD 202generates audio signals reflecting the progress of placing a call (e.g.,sounds indicating the number being dialed or transmitted to the network,a ringback tone while waiting for a called party to answer, etc.), thosesounds can be delivered via line-out to accessory 204, allowing the userto monitor progress of making the call just as if the call had beenplaced by interacting directly with MCD 202.

Audio processing at block 518 can continue while at block 520 accessory204 can continually monitor or periodically check to determine if theuser has requested that the call should end. For example, the user mayoperate a “hang up” control on accessory 204. If the user requests thatthe call should end, at block 522, accessory 204 can notify MCD 202 toend the call, e.g., by sending a ButtonStatus command as described abovewith the bit corresponding to “Hang Up” set or by sending a specificEndCall command or the like. At block 524, accessory 204 can check foran end-call notification from MCD 202. MCD 202 may send the end-callnotification, e.g., in response to the end-call instruction fromaccessory 204 at block 522 or in response to termination of the call bythe mobile communication network (e.g., if the other party hangs up orthe connection is lost). If no end-call notification is received atblock 524, process 500 can return to block 518 to continue duplex-modeaudio for the call.

Once the end-call notification is received at block 524, accessory 204can disable its internal echo cancellation and resume the line-insimplex mode (or other audio mode that was enabled prior to placing thecall) at block 526; process 500 can return to block 508 to resumeplayback of audio or other operation that may have been in progress whenthe call was placed.

FIG. 6 is a flow diagram of a process 600 for handling a telephone callplaced using an accessory device according to an embodiment of thepresent invention. Process 600 can be executed by MCD 202 whileaccessory 204 executes process 500.

Process 600 can start when MCD 202 becomes connected to accessory 204.At block 602, MCD 202 establishes communication with accessory 204. Aswith other processes described above, block 602 can includeidentification and authentication in accordance with the communicationprotocol. At block 604, MCD 202 can obtain capability and initial stateinformation from accessory 204. In particular, accessory 204 canindicate whether it provides a microphone, whether it is capable ofoperating in a duplex mode, whether it provides echo cancellation, andwhether it intends to use remote control commands to control the MCD;accessory 204 can also provide any other applicable information aboutits capabilities, including other audio processing capabilities such asnoise reduction. Accessory 204 can also provide initial-stateinformation, e.g., whether it will begin operations in line-out simplexmode or some other mode. In some embodiments, accessory 204 can provideany or all of its capability and initial state information as part ofestablishing communication at block 602. In some embodiments, process600 continues only if accessory 204 supports duplex mode and echocancellation and also uses remote control commands.

At block 606, MCD 202 can begin delivering audio signals via theline-out path to accessory 204. For example, a user might operate MCD202, either directly or using a remote control feature supported byaccessory 204, to select one or more audio or video tracks for playback.MCD 202 can route the audio portion of the track to accessory 204.Delivery of audio signals to accessory 204 can continue indefinitely.Delivering line-out to accessory 204 at block 606 is appropriate ifaccessory 204 initially operates in line-out simplex mode or anothermode in which it can receive line-out; in other embodiments, accessory204 can initialize to a different audio mode, and MCD 202 may signalaccessory 204 to enter line-out simplex mode before delivering audio atstep 606. Alternatively, block 606 can involve other audio operations(e.g., recording from accessory 204) or simply waiting with both line-inand line-out disabled.

At block 608, MCD 202 can receive a phone-dialing command from accessory204. In various embodiments, any of the commands described above orother commands can be received. At block 610, MCD 202 can send abegin-call notification to accessory 204; for instance, any of thenotifications described above as signaling that accessory 204 shouldenter duplex mode can be used. At block 612, MCD 202 can place the call,and in some embodiments, playback of other audio on line-out toaccessory 204 can be paused while the call is placed. MCD 202 can placea call in various ways. For instance, MCD 202 can “dial” a number bytransmitting it onto the mobile communication network in the form of arequest for a connection to the specified number. MCD 202 can then waitfor a telephone connection to be established on the network. In themeantime, at block 614, MCD 202 can begin directing call-related audioto the line-out path so that it is delivered to the accessory. Thus, forexample, MCD 202 can generate audio signals corresponding to“touch-tone” sounds indicating the number being transmitted onto thenetwork and can generate signals corresponding to a ringback tone whilewaiting for the called party to answer. Such signals can be deliveredvia line-out to the accessory, allowing the user to hear the progress ofthe call being placed. Once the call connects, audio signals receivedvia the mobile communication network can be processed and delivered viathe line-out path to accessory 204; such processing can be similar toblock 316 of process 300 (FIG. 3) described above.

Once the call connects, MCD 202 can begin processing received audiosignals on line-in and transmitting the processed signals to the mobilecommunication network (block 616). Such processing can be similar toblock 318 of process 300 described above. It is to be understood thatacts associated with blocks 614 and 616 can be performed simultaneouslyor concurrently, thereby supporting duplex audio. Further, in thisembodiment MCD 202 need not perform echo cancellation or any other audioprocessing that would conflict with processing by accessory 204.

At block 618, MCD 202 can determine whether the call should bedisconnected. In one embodiment, the call can become disconnectedwithout ever being truly connected (e.g., if the network or the calledparty fails to respond during placing the call at block 612 and the calldoes not divert to a voice mail or other automated answering system). Inother embodiments, MCD 202 can receive a command from accessory 204indicating that the call should be ended, e.g., as described above. Instill other embodiments, MCD 202 can detect that the call has beenterminated by the mobile communication network. As long as the callcontinues, MCD 202 can continue to execute blocks 614 and 616, allowingthe user to speak and listen via accessory 204.

Once MCD 202 determines that the call should end, MCD 202 can send anend-call notification to accessory 204 at block 620; any of thenotifications described above as signaling that accessory 204 shouldexit duplex mode can be used. Thereafter, the accessory can revert toline-out simplex mode (or other audio mode it may have been using priorto the call), and process 600 can return to block 606 to provide furtheraudio to accessory 204. For example, MCD 202 can resume playback of atrack that was paused when the call was initiated.

It will be appreciated that processes 500 and 600 are illustrative andthat variations and modifications are possible. Steps described assequential may be executed in parallel, order of steps may be varied,and steps may be modified, combined, added or omitted. For instance, asnoted above, the accessory can operate in a mode other than line-outsimplex mode when a call is not in progress; at the end of a call, theaccessory can revert to the mode it was operating in prior to the call.Also as noted above, the techniques described herein can be used toregulate various aspects of audio processing behavior in addition to orinstead of echo cancellation so that the accessory and the mobilecommunication device are in coordination as to what processing is to bedone by which device.

Other techniques can also be used to place a call. For instance, ifaccessory 204 and MCD 202 support remote browsing of contacts stored onMCD 202 via the user interface of accessory 204, a user can operateaccessory 204 to select a contact to be called; accessory 204 can send acommand to MCD 202 identifying the contact to be called; and MCD 202 canaccess a database of contact information (e.g., in storage device 210)to place the call. In another embodiment, accessory 204 can maintain itsown database of contacts, and the user may select a contact to call fromthat database.

Further, techniques similar to those described above can be used tocoordinate audio processing between a mobile communication device and anaccessory in contexts other than making and/or receiving phone calls.For example, referring again to FIG. 2, in another embodiment, accessory204 and MCD 202 can interoperate to provide a karaoke machine. In oneimplementation, MCD 202 can play a song while a user sings intomicrophone 242 of accessory 204 (or an external microphone connected toaccessory 204). The signal from microphone 242 can be delivered vialine-in to MCD 202, which can mix the line-in signal with the audiosignal of the song (e.g., in audio section 214 or processor 206) androute the mixed signal to line-out for delivery to speakers 240 ofaccessory 204. In some embodiments, MCD 202 can also display song lyricsand/or provide timing prompts to the user (e.g., changing color of thedisplayed lyrics as the words are to be sung). Similarly, MCD 202 caninteroperate with accessory 204 as a mixing board, with accessory 204providing, via the line-in path, a signal (e.g., corresponding to avoice, instrument, or any other audio source) that is to be mixed withan audio signal generated by MCD 202 and delivered back to accessory 204as a line-out signal.

More generally, in a number of different situations, an accessory devicecan operate in duplex mode and the line-in signal to a mobilecommunication device can be looped back onto the line-out path by themobile communication device, either alone or in combination with anothersignal. In such situations, embodiments of the present invention canallow the mobile communication device and accessory to coordinate audioprocessing for optimum sound.

FIG. 7 is a message passing diagram illustrating coordination of audioprocessing between a mobile communication device and an accessoryaccording to an embodiment of the present invention. Left-hand column702 represents actions taken by a mobile communication device such asMCD 202 of FIG. 2; right-hand column 704 represents actions taken by anaccessory device such as accessory 204 of FIG. 2. The MCD and theaccessory can connect and exchange capability information as describedabove (not explicitly shown in FIG. 7) to establish an initial operatingcondition. In some embodiments, the initial operating condition can be aline-out simplex mode in which the MCD sends line-out to the accessory(block 706) and the accessory receives the line-out (block 708) or aline-in simplex mode in which the accessory sends line-in to the MCD(block 708) and the MCD receives the line-in (block 706).

At some point (block 710), the MCD can detect that the accessory shouldswitch to duplex mode. For example, as described above, a phone call maybe placed or received, or the user may launch a karaoke application,mixing-board application or other application in which the accessoryshould operate in duplex mode. Accordingly, at block 712, the MCD cannotify the accessory to enter duplex mode and enable echo cancellation.In some embodiments, the notification at block 712 may also notify theaccessory to enable noise reduction and/or any other audio processingthat it is desirable for the accessory to perform when in duplex mode.At block 714, the accessory can respond to the notification by enteringduplex mode and enabling echo cancellation (and/or other audioprocessing), while at block 716, the MCD disables its own internal echocancellation (and/or any other audio processing that has been designatedto be handled by the accessory when in duplex mode).

The MCD and accessory can proceed to operate in duplex mode (blocks 718,720), with the MCD receiving an audio signal via the line-in path fromthe accessory while sending an audio signal via the line-out path to theaccessory; conversely, the accessory can send an audio signal via theline-in path to the MCD while receiving an audio signal via the line-outpath from the MCD. During duplex-mode operation, the accessory can applyecho cancellation and/or any other audio processing that has beendesignated to be handled by the accessory while in duplex mode.

While operating in duplex mode, the MCD can detect (block 722) thatduplex mode operation should end. For instance, a phone call may bedisconnected, or the user may exit an application program that usesduplex mode such as karaoke or mixing board applications. When duplexmode operation should end, the MCD can signal the accessory (block 724)to exit duplex mode and disable echo cancellation (and/or any otheraudio processing that the accessory performs only in duplex mode). Atblock 726, the accessory exits duplex mode. In one embodiment, whenduplex mode is exited, the accessory can restore a simplex mode that itwas operating in prior to entering duplex mode. Accordingly, the MCD andthe accessory can return to the state depicted by blocks 706, 708. In analternative embodiment, the MCD can signal the accessory to transitionto a different audio state upon exiting duplex mode, depending on whatactivity is expected to occur next.

In other embodiments, a user can receive a text message by interactingwith an accessory rather than directly with a mobile communicationdevice. FIG. 8 is a flow diagram of a process 800 for handing textmessages using an accessory device according to some embodiments of theinvention. Process 800 can be executed by an accessory (e.g., accessory204 of FIG. 2) that is connected to a mobile communication device (e.g.,MCD 202 of FIG. 2). A text message, for example, can be an SMS messageand/or an MMS message.

Process 800 can start when accessory 204 becomes connected to MCD 202.At block 802, accessory 204 establishes communication with MCD 202. Aswith process 400 described above, block 802 can include identificationand authentication in accordance with the communication protocol. Atblock 804, accessory 204 can provide capability information to MCD 202.In particular, accessory 204 can indicate whether it is capable ofreceiving and/or displaying text messages. Moreover, accessory 204 canindicate whether it is capable of receiving and/or displaying full textmessages, partial text messages, multimedia text messages (MMS), and/orcontact information associated with the text message. Accessory can alsoindicate whether it want to receive text message notifications. Forexample, an accessory can register with MCD 202 to receive text messagenotifications. Furthermore, accessory 204 can indicate whether itintends to use remote control commands to control MCD 202. Accessory 204can also provide any other applicable information about its capabilitiesat block 804. In some embodiments, process 800 continues only ifaccessory 204 supports text messaging.

At block 806, accessory 204 can receive a text message notification fromMCD 202. A text message notification can indicate to accessory 204 thata text message has been received at MCD 202. In some embodiments, a textmessage notification can include an identifier associated with the textmessage, the phone number from where the text message was sent, at leastsome contact information, multimedia, a flag indicating multimedia isassociated with the text message, the full text message, and/or aportion of the text message. Process 800 can remain at block 806indefinitely, or until a text message notification is received from MCD202. While at block 806, accessory can perform other tasks, such asmedia playback, etc.

At block 808, accessory 204 can notify the user that a text message hasbeen received. In some embodiments, such notifications can be turned offat accessory 204 by the user. If the notifications are turned off, insome embodiments, then process 800 can end. In some embodiments, theuser can be alerted and queried whether the user would like to view thetext message through a user interface (e.g., user interface 234). Usernotifications can also include displaying a text message notice on adisplay, displaying a portion of the text message on a display,displaying contact information associated with the text message on adisplay, displaying the phone number associated with the text message ona display, and/or displaying the time the text message was received on adisplay, etc. In other embodiments, the user can be notified throughaudible signals such as a ring tone or other sound through a speaker orspeakers. In other embodiments, the user can be notified throughvibration. Various other sensory notifications can be used.

At block 810, the user can indicate through a user interface (e.g., userinterface 234) a desire to view the text message. In some embodiments,the user can press a physical button and/or a icon on a touch screendisplay that indicates a desire to view the text message or not. In someembodiments, a lack of user response can indicate that the user does notdesire to view the text message and process 800 can return to block 806and await a text message notification. If the user wishes to view thetext message, then the text message can be displayed at block 812. Insome embodiments, contact information associated with the sender of thetext message including name, phone number, and/or photographs can bedisplayed as well.

In some embodiments, a listing of text messages available at MCD 202 canalso be requested by the accessory and upon receipt displayed to theuser. The user can select a message from the listing of text messagesfor viewing. In some embodiments, the listing of text messages caninclude the phone number associated with the text message, the name ofthe sender of the text message, and/or a portion of the text message.

At block 814, if the text message notification from MCD 202 indicatesthat the text massage includes multimedia, for example, audio, video,and/or images, etc., then a command can be sent to MCD 202 fromaccessory 204 requesting the media at block 816. For example, a GetMediacommand can be sent from accessory 204 to MCD 202 that can include atext message identifier and/or a media identifier. As another example, aGetTextMessage command can be sent that includes a text messageidentifier and/or a bit mask that indicates, by asserting a bit (orbits) within the bitmask, a request for the associated media. In someembodiments, if the text message includes media (e.g., an MMS message)then the user can be queried whether he would like to view or hear themedia. The media can be sent from MCD 202 to accessory 204 and thenpresented to the user through user interface 234 at block 818. Process800 can continue indefinitely by returning to block 806 or untilaccessory 204 and MCD 202 become disconnected.

In the embodiments discussed in relation to FIG. 8, the text messagenotification can include the full text message. In some embodiments, thetext message notification can include a portion of the text message.FIG. 9 is a flow diagram of a process 900 for handing a portion of atext messages using an accessory 204 device according to someembodiments of the invention. For example, SMS text messages can includeup to 160 characters. In process 800 all characters (e.g., up to 160characters) are sent to accessory 204 in the text message notificationmessage. In process 900 a lesser portion of the text message can beincluded in the text message notification message. As an example, thetext message notification can include 20, 30, 40, 50, 60, 70, 80, 90 or100, characters etc.

Blocks 902, 904, 906, and 908 can be implemented similarly to blocks802, 804, 806, and 808 respectively. At block 910 a partial text messagecan be displayed at the user interface 234. Contact information, forexample, a phone number and/or contact name associated with a sender ofthe text message, can also be displayed. At block 912 the user can electto view the full text message through user interface 234, if the fulltext message is not already displayed. In some embodiments, the user canpress a physical button and/or an icon on a touch screen display thatindicates whether view the full text message should be displayed or not.In some embodiments, the user can simply ignore the notification toindicate that he would not like to view the full text message andprocess 900 can return to block 906 and await a text notification fromMCD 202.

At block 914 the full text message can be requested from MCD 202 byaccessory 204. For example, accessory 204 can send a GetTextMessagecommand to MCD 202 requesting the full text message. The GetTextMessagecommand can include a bitmask that indicates that the full text messageis requested. The full text message can then be received at accessory204 at block 916 and displayed to a user through user interface 234 atblock 918.

At block 920, if the text message notification from MCD 202 indicatesthat the text massage includes multimedia, for example, audio, video,and/or images, etc., then a command can be sent to MCD 202 fromaccessory 204 requesting the media at block 922. For example, a GetMediacommand can be sent from accessory 204 to MCD 202 that can include theassociated text message identifier and/or a media identifier. As anotherexample, the GetTextMessage command can be sent that includes theassociated text message identifier and/or a bit mask indicating arequest for the associated media. In some embodiments, accessory 204 canrequest the full text message and the media using a singleGetTextMessage command, for example, by asserting the appropriate bit(or bits) in a bitmask associated with receiving the text message andthe media. In some embodiments, if the text message includes media(e.g., an MMS message), then the user can be queried whether he wouldlike to view or hear the media. The media can be sent from MCD 202 toaccessory 204 and then presented to the user through user interface 234at block 924.

In some embodiments, accessory 204 can query the user whether he wouldlike to respond to or forward the text message at block 926. If the userchooses to reply to or forward the text message, then accessory 204 canreceive data for replying and/or forwarding at block 928. For example,if the user elects to reply to the text message, accessory 204 canprovide a text entry field on a display and receive text from the userthrough a keypad and/or a touch screen to send as a reply. As anotherexample, if the user would like to forward the text message, accessory204 can provide a text entry field on a display for receiving a phonenumber or for receiving a contact name to forward the text message to.At block 930 a command can be sent to MCD 202 to reply to or forward thetext message. For example, the SetTextMessage command can be used withthe bits in a bitmask corresponding to either reply to or forwardasserted, along with the text message identifier, the text received fromthe user, the contact name and/or phone number received from the user.

At block 932 the user can chose to delete the text message. At block 934the accessory can send a command to MCD 202 to delete the message. Forexample, the DeleteTextMessage command can be used with a bit assertedthat is associated with deleting the text message along with the textmessage identifier. Process 900 can then return to block 906 to awaitnotification of a text message or until accessory 204 and MCD 202 becomedisconnected.

FIG. 10 is a flow diagram of process 1000 for sending text messages toan accessory from a mobile communication device according to someembodiments of the invention. In this embodiment, before a text messageis received, a mobile communication device can be connected to accessory204. For example, accessory 204 might be operating as a speaker dock,playing audio content stored on MCD 202 or performing any number ofother functions.

Process 1000 can start when accessory 204 becomes connected to MCD 202.At block 1002, MCD 202 establishes communication with accessory 204. Insome embodiments, establishing communication can include identificationand authentication in accordance with the communication protocol. Atblock 1004, MCD 202 can obtain capability information from accessory204. For example, accessory 204 can indicate whether it provides amicrophone, whether it is capable of operating in a duplex mode, andwhether it provides echo cancellation; accessory 204 can also provideany other applicable information about its capabilities, including otheraudio processing capabilities such as noise reduction. In someembodiments, accessory 204 can indicate whether it supports receivingtext messages and/or register with the MCD for such notifications. Insome embodiments, accessory 204 can provide any or all of its capabilityinformation as part of establishing communication at block 302. In someembodiments, process 1000 continues only if accessory 204 supportsreceiving text messages from MCD 202.

At block 1006, MCD 202 detects a text message (in this example, anincoming text message) and can generate an alert for the user. Forexample, MCD 202 can pause the playback of any currently playing trackand play a ring tone, display a message, vibrate, and/or take otheraction to alert a user to an incoming phone call. In some embodiments,MCD 202 can exit or suspend operation of an application operating on MCD202 in order to alert a user. At block 1008 the text message can bestored in memory (e.g., storage device 210) and/or associated with atext message identifier. At block 1010 MCD 202 determines whetheraccessory 204 accepts text messages, for example, as determined from thecapability information received from accessory 204 at block 1004. Inother embodiments, at block 1010 MCD 202 can determine whether accessory204 registered to receive text message notifications.

At block 1012 MCD 202 can send a text message notification to accessory204. In some embodiments, the text message notification can include aportion of the text message, the sender's phone number, contactinformation associated with the text message, the full text message, atext message identifier, an indication that the text message includesmedia, etc. At block 1014, in some embodiments, MCD 202 can receive arequest for the full text message. In embodiments where the text messagenotification includes only a portion of the text message, MCD 202 canreceive a request for the rest of the text message at block 1014,retrieve the text message from memory at block 1016, and send the fulltext message at block 1018. Moreover, MCD 202 can also send contactinformation such as the sender's name. The sender's name can beidentified by matching the sender's phone number with a contacts phonenumber stored in memory.

If the text message notification indicates that the text messageincludes media, at block 1020 MCD 202 can receive a request for themedia. If a request is not received, then process 1000 can continue toblock 1024. However, if a request is received at block 1020, then themedia can be sent to accessory 204 at block 1022. For example, the mediacan be retrieved from memory using the text message identifier. In someembodiments, the media can include audio and/or video. In suchembodiments, the audio and/or video can be streamed to accessory 204using an audio and/or video connection, if such capability is supportedby accessory 204 as indicated in block 1004.

In some embodiments, a user can reply to and/or forward a text messagefrom accessory 204. If the user elects to reply to and/or forward a textmessage, then MCD 202 can receive a message indicating that MCD 202should reply to and/or forward the text message at block 1024. Forexample, the SendTextMessage command can be used with the proper bit(s)asserted in a bitmask to indicate whether to reply to and/or forward thetext message along with the text message identifier. The SendTextMessagecommand, for example, can also include a phone number, a contact name, areply message, etc. A text message can be composed at block 1026. If themessage indicates that the text message should be forwarded, theSendTextMessage command, for example, can specify the name and/or numberwhere the text message should be forwarded. In the event a contact nameis specified, MCD 202 can look up the appropriate phone number. If themessage indicates that the text message should be replied to, theSendTextMessage command, for example, can specify a reply text message.At block 1028, the forward and/or reply text message can be sent throughthe telephone interface (e.g., RF section 212 of FIG. 2).

In some embodiments, the user may wish to delete the text message. Ifso, MCD 202 can receive a message that specifies that the text messageshould be deleted at block 1030. For example, the DeleteTextMessagecommand can be used with the proper bit(s) asserted in a bitmask toindicate that the text message should be deleted. The DeletetextMessagecommand can also include a text message identifier. Upon receipt of themessage, MCD 202 can delete the text message associated with the textmessage identifier. For example, MCD 202 can delete the text messagefrom memory. Process 1000 can continue indefinitely, e.g., untilaccessory 204 and MCD 202 become disconnected.

While processes 800, 900 and 1000 have been described with respect totext messages, similar processes can be implemented for handling e-mailmessages. For example, emails can be received from a communicationnetwork at the MCD, a notification can be sent from the MCD to theaccessory indicating that an email has been received, a request to viewat least a portion of the email can be sent to the MCD from theaccessory, the email can be sent to the accessory, and viewed at theaccessory by a user. In some embodiments, the email address of thesender can be sent to the accessory and/or displayed. In someembodiments, a user can reply to, forward, and/or delete emails usingthe accessory.

In other embodiments, a user can receive a voicemail message byinteracting with an accessory rather than directly with a mobilecommunication device. FIG. 11 is a flow diagram of process 1100 forhandling voicemail using an accessory device according to someembodiments of the invention. Process 1100 can be executed by anaccessory (e.g., accessory 204 of FIG. 2) that is connected to a mobilecommunication device (e.g., MCD 202 of FIG. 2).

Process 1100 can start when accessory 204 becomes connected to MCD 202.At block 1102, accessory 204 establishes communication with MCD 202. Aswith process 400 described above, block 1102 can include identificationand authentication in accordance with the communication protocol. Atblock 1104, accessory 204 can provide capability information to MCD 202.In particular, accessory 204 can indicate whether it is capable ofreceiving and/or playing voicemail messages, for example, by registeringwith MCD 202 for voicemail notifications. Accessory 204 can also provideany other applicable information about its capabilities at block 1104.In some embodiments, process 1100 continues only if accessory 204 hasregistered for voicemail notifications.

At block 1106, accessory 204 can receive a voicemail notification fromMCD 202. A voicemail notification can indicate to accessory 204 that avoicemail has been received at MCD 202. In some embodiments, a voicemailnotification can include an identifier associated with the voicemail,the phone number from where the voicemail was sent, and/or contactinformation associated with the sender (e.g., the sender's name).Process 1100 can remain at block 1106 indefinitely, or until a voicemailnotification is received from MCD 202.

At block 1108, accessory 204 can notify the user that a voicemail hasbeen received by MCD 202. In some embodiments, such notifications can beturned off at accessory 204 by the user. In other embodiments, accessory204 can register with MCD 202 to receive voicemail notifications. If thenotifications are turned off, in some embodiments, then process 1100ends. In some embodiments, the user can be notified and the user can bequeried if he would like to hear the voicemail through a user interface(e.g., user interface 234). In other embodiments, such notifications caninclude displaying a notice on a display, displaying contact informationassociated with the voicemail on a display, displaying the phone numberassociated with the voicemail on a display, and/or displaying the timethe voicemail was received on a display, etc. In other embodiments, theuser can be notified through audible signals such as a ring tone orother sound through a speaker or speakers. In other embodiments, theuser can be notified through vibration or other sensory notification.

At block 1110, the user can indicate through a user interface (e.g.,user interface 234) that he would like to hear the voicemail. In someembodiments, the user can press a physical button and/or a icon on atouch screen display that indicates that a desire to hear the voicemailor not. In some embodiments, the user can simply ignore the notificationto indicate that he would not like to view the voicemail and process1100 can end. If the user elects to hear the voicemail message, at block1112 accessory 204 can request a voicemail list from MCD 202. Forexample, a GetVoicemailList command can be sent to MCD 202 indicatingthat a listing of voicemails is requested. For example, theGetVoicemailList command can include a bitmask with a bit (or bits)asserted that indicates a listing of available voicemails should be sentto accessory 204. In some embodiments, a voicemail list can be includedin the voicemail notification received at block 1106. The voicemail listcan include a listing of voicemails, the sender's phone number and/orcontact information, date and/or time the voicemail was received, lengthof the message, and/or a voicemail indicator. At block 1114 a visualrepresentation of the available voicemails from the voicemail list canbe displayed on accessory 204. For example, accessory 204 can displaythe contact name and the time the message was received.

At block 1116 a voicemail can be selected from the listing of voicemailby a user. A voicemail can be selected, for example, through userinterface 234. In some embodiments, block 1116 can repeat indefinitelyuntil the user selects a voicemail message. The voicemail identifierassociated with the selected voicemail message can then be sent to MCDat block 1118. For example, the GetVoicemail command can be used with abit (or bits) asserted that indicates a voicemail.

In some embodiments, an accessory can bypass blocks 1112, 1114 and 1116.That is, at block 1110 the accessory can send the GetVoicemail commandindicating that the user would like to hear the voicemail associatedwith voicemail notification. In this embodiment, a listing of voicemailsis not provided.

In some embodiments, playback controls can be provided at user interface234 of accessory 204 at block 1120. Playback controls can provide a userbuttons and/or icons to pause, play, stop, fast forward, rewind, adjustthe volume, etc., of a voicemail. At block 1121, accessory 204 caninitialize its audio state, e.g., in line-out simplex mode. In thismode, accessory 204 can receive line-out from MCD 202 but does notprovide line-in to MCD 202; in some embodiments, audio section 236 ofaccessory 204 disables sending of signals onto the line-in path while inline-out simplex mode. Line-out simplex mode supports various operationsnot requiring two-way audio. This line-out mode between MCD 202 andaccessory 204 can be used to stream the voicemail from MCD 202 toaccessory 204 at block 1122. The voicemail stream can be played fromaccessory 204 at block 1124. For example, the voicemail can be playedthrough speakers and/or headphones at the accessory.

The user can modify the playback of the voicemail by using the playbackcontrols displayed at block 1120. At block 1126 a playback control canbe selected. For example, the user can chose to pause, stop, play, fastforward, rewind, slow down, speed up, and/or adjust the volume of thestreaming voicemail by sending a message to MCD 202 at block 1128. Forexample, the ButtonStatus command can be used to communicate playbackcontrol from accessory 204 to MCD 202. For example, a bit can beasserted to indicate that playback of the voicemail should be paused.Another bit, for example, can be asserted to indicate that playback ofthe voicemail should be fast forwarded. MCD 202 can provide the requiredplayback control as indicated in the message.

A user can also choose to delete a voicemail in the voicemail list, byso indicating though user interface 234, for example, by pressing ortouching a button or icon at block 1130. If the user chooses to delete avoicemail, the voicemail may be selected by the user in the list orother wise specified by the user. At block 1132 a delete command can besent to MCD 202 from accessory 204 that includes the voicemailidentifier. For example, DeleteVoiceMail command can also be used byasserting the proper bit in a bitmask and including the voicemailidentifier. At block 1134, accessory 204 can then remove the voicemailfrom the voicemail list that was displayed at block 1114. In someembodiments, MCD 202 can resend the voicemail list and accessory 204 canredisplay the list in response to deleting a voicemail.

At block 1136 the user can choose to call back the phone number fromwhich the voicemail was received. If the user so chooses, at block 1138a callback command can be sent to MCD 202, for example, using theDialNumber command. In some embodiments, a notification can be receivedat the accessory, for example, like the indication discussed at block514 of FIG. 5, indicating whether the call was successfully connected.Accessory 204 can then enter duplex audio mode at block 1140. If thecall is connected by MCD 202, then audio can be sent and receivedthrough user interface 234 at block 1142, until the call ends at block1144. At block 1146 if the voicemail stream has ended, then process 1100can return to block 1106, otherwise, process 1100 can return to block1126. In some embodiments, even after the voicemail stream has ended,playback control functions, delete functions, and/or call back functionscan still be accessed by the user.

FIG. 12 is a flow diagram of process 1200 for sending voicemail toaccessory 204 from MCD 202 according to some embodiments of theinvention. At block 1202, MCD 202 can establish communication withaccessory 204 in a manner similar to those discussed above. At block1204, MCD 202 can obtain accessory capability information from accessory204 as described above. For example, MCD 202 can receive informationdictating whether accessory 204 can receive voicemails.

At block 1206, a voicemail is received at MCD 202 and the voicemail canbe stored in memory (e.g., in storage device 210) at block 1208. Thevoicemail can also be associated with a voicemail identifier, which canbe associated with the voicemail in memory. Process 1200 can remain atblock 1206 indefinitely, or until a voicemail is received. Moreover,various other processes and/or information communicated betweenaccessory 204 and MCD 202 while process 1200 remains at block 1206.

MCD 202 can determine whether accessory 204 has registered with MCD 202to accept voicemails at block 1210. If accessory 204 is not configuredto accept voicemail messages, then process 1200 ends. If accessory 204is configured to accept voicemail messages, then a voicemailnotification can be sent to accessory 204. In some embodiments, avoicemail notification can include an identifier associated with thevoicemail, the phone number from where the voicemail was sent, and/orsome contact information.

MCD can then wait until it receives a request for a voicemail list atblock 1214. Process 1200 can remain at block 1214 indefinitely, or untilrequest for a voicemail listing is received. In response to the requestfor the voicemail listing, at block 1206 MCD 202 can send a listing ofthe available voicemails that includes, for example, contactinformation, a voicemail identifier, the time the voicemail wasreceived, etc.

MCD can then wait until it receives a request for a specific voicemailwithin the voicemail list at block 1218. The request can include thevoicemail identifier. For example, the GetVoiceMail command can be usedwith a bit asserted within a bitmask that indicates a request for avoicemail along with the voicemail identifier. Process 1200 can remainat block 1218 indefinitely, or until request for a specific voicemail isreceived. In some embodiments, process 1200 can timeout and end after aspecific period of time. In response to the request for a voicemail, atblock 1219 MCD 202 can retrieve the selected voicemail from memory. Atblock 1220, the voicemail can be streamed to accessory 204 using anaudio line-out.

At block 1221, MCD 202 can receive a playback control command fromaccessory 204. For example, such a command can be issued from accessory204 at block 1128. In some embodiments, a playback control command caninclude, fast-forward, rewind, play, pause, stop, and/or volumecommands. For example, the ButtonStatus command can be used with a bit(or bits) associated with playback control asserted. At block 1222, MCD202 can respond by controlling playback accordingly.

At block 1224, MCD 202 can receive a call back command from accessory204. For example, such a command can be issued from accessory 204 atblock 1138. For example, the VoiceMail command can be used with a bit(or bits) associated with callback asserted. In other embodiments, theDialNumber command can also be used. At block 1227 the phone call isinitiated by MCD 202 to the phone number associated with the voicemailover a mobile communication network (e.g., using RF section 212). Atblock 1229 audio line-out to accessory can be established and audio fromthe phone call can be sent to accessory 204. At block 1230 audio fromaccessory 204 can be processed and transmitted to the mobilecommunication network. Blocks 1229 and 1230 can repeat until the phonecall is disconnected at block 1231.

At block 1232, MCD 202 can receive a delete command from accessory 204.For example, such a command can be issued from accessory 204 at block1132. For example, the DeleteVoiceMail command can be used with a bit(or bits) associated with the delete command asserted. At block 1234,the voicemail can be removed from memory. In some embodiments, avoicemail can be moved to a deleted voicemail folder rather than beingcompletely removed.

At block 1240 if the voicemail stream has ended then process 1200 canreturn to block 1206 and await another voicemail, otherwise, process1200 can return to block 1221. In some embodiments, even after thevoicemail stream has ended, playback control functions, deletefunctions, and/or call back functions can still be performed.

In some embodiments, communication-related notifications can be sent toan accessory from a mobile communication device that alerts theaccessory that incoming communications are available. In someembodiments, prior to receiving notifications, an accessory can registerwith the MCD specifying the type of communication-related notificationsthe accessory wants to receive. In some embodiments, the accessory(often in conjunction with a user) can then respond to the MCDrequesting that the MCD forward the message to the accessory and presentthe communication to the user.

In some embodiments, an MCD may not be capable of receiving a voicemailfrom a mobile communication network. Instead, the MCD can receive anotification from the mobile communication network that a voicemail hasbeen received. The voicemail can be stored by the mobile communicationnetwork, (e.g., using a server). In order to hear the voicemail a usercan dial his voicemail number and possibly enter a passcode. Followingwhich, the voicemail can be played from a server through the mobilecommunication network. In some embodiments, an accessory can access avoicemail through the mobile communication network. FIG. 13 shows a flowdiagram of process 1300 for accessing voicemail through the mobilecommunication network using accessory 204 coupled with MCD 202.

Blocks 1302, 1304, 1306, and 1308 can be implemented similarly to blocks1102, 1104, 1106, and 1108. At block 1310 the user can elect to hear thevoicemail. If the user does not elect to hear the voicemail, thenprocess 1300 returns to block 1306 and awaits a voicemail notification.Process 1300 can remain at block 1306 indefinitely or until accessory204 is disconnected from MCD 202. If the user elects to hear thevoicemail, then accessory 204 can send a request to MCD 202 requestingto hear the voicemail at block 1312 and accessory 204 can enter line-outsimplex mode at block 1314 as described above. This line-out modebetween MCD 202 and accessory 204 can be used to stream the voicemailfrom MCD 202 to accessory 204 at block 1316 and/or send dual-tonemulti-frequency (DTMF) tones to the MCD. In some embodiments, accessory204 can enter line-out simplex mode and receive voicemail audio withoutsending any data to MCD 202. The voicemail stream can be played fromaccessory 204 at block 1318. For example, the voicemail can be playedthrough speakers and/or headphones at the accessory.

At block 1318 user input can be entered at the accessory. Typically,during a voicemail call the user can navigate between voicemail optionsand commands by pressing a button or a series of buttons. Accordingly,if the user presses one or more buttons while listening to the voicemailat block 1320, then accessory 204 can send the user input to MCD 202 atblock 1322. For example, the accessory can send DTMF tones to MCD 202that corresponds with telephone buttons. In some embodiments, theButtonStatus command can be used to communicate data from the accessory.If the voicemail stream ends, as determined at block 1324, then process1300 can return to block 1306, otherwise process 1300 returns to block1318.

FIG. 14 shows a flow diagram of process 1400 for allowing accessory 204to access voicemail through MCD 202 according to some embodiments.Process 1400 can be used in conjunction with an accessory executingprocess 1300. Blocks 1402 and 1404 can be implemented similarly toblocks 1202 and 1204. At block 1406 a voicemail notification can bereceived form a mobile communication network indicating that a voicemailis saved at a server that can be accessed through the mobilecommunication network.

MCD 202 can determine whether accessory 204 has registered with MCD 202to accept voicemails at block 1410. If accessory 204 is not configuredto accept voicemail messages, then process 1400 can return to block1406. If accessory 204 is configured to accept voicemail messages, thena voicemail notification can be sent to the accessory at block 1412. Inresponse to the voicemail notification, the accessory can send a requestto receive and/or call the voicemail (e.g., at block 1312), which can bereceived by MCD 202 at block 1414.

If a request is received from accessory 204, then MCD 202 can call thevoicemail server and communicate voicemail audio to the user throughaccessory 204. Blocks 1416, 1418, 1420, 1422, 1424, and 1426 can beimplemented similarly as blocks 606, 608, 610, 612, 614, and 616respectively. In these blocks, a mobile phone connection can beestablished with a voicemail server and the audio data sent to and froman accessory device through MCD 202. At block 1428, if the call is notdisconnected, then process 1400 returns to block 1426. In someembodiments, at block 1420 the MCD can notify the accessory to entersimplex mode. In some embodiments, at block 1420, the MCD can requestthat the accessory enable echo cancellation.

If user input is received at block 1430, for example, DTMF data fromaccessory 204 (e.g., at block 1322), then process 1400 can send DTMFdata to the voicemail server at block 1432. In some embodiments, userinput may not be DTMF data. For example, user input can be communicatedto MCD 202 using the ButtonStatus command. As another example, user datacan include a bitmask or byte representing a digit that can be convertedinto a DTMF tone by MCD 202. Once received at the server, DTMF data canbe used by the server to modify playback of the voicemail. At block1434, if the call is disconnected a call-end notification can be sent tothe accessory at block 1436, otherwise process 1400 returns to block1426.

In some embodiments, a user can place and/or receive a phone call to anMCD using an accessory, as discussed in regard to FIGS. 3-7. In someembodiments, a phone call can be made that connects with an automatedserver that can respond to DTMF responses from a user (e.g., a phonetree). In some embodiments, DTMF signals can be sent to the MCD from theaccessory and then to the automated server. In other embodiments, theaccessory can send an indication specifying a phone number or a DTMFtone (e.g., sending a byte or bitmask that corresponds with thedifferent tones). In response, the MCD can produce the DTMF tone andsend it to the server.

While the invention has been described with respect to specificembodiments, one skilled in the art will recognize that numerousmodifications are possible. For instance, audio signals can include anysignal that provides a representation of sound in any format, includinganalog or digital formats. Audio signals can represent sound informationany encoding desired, provided that the mobile communication device andaccessory 204 are equipped with appropriate hardware and/or software forencoding and decoding the audio signals. Further, audio signals referredto as line-in and line-out may include monaural, stereo, andmulti-channel (e.g., so-called “5.1” or “7.1”) signals. Audio signalpaths can be wired and/or wireless (e.g., using a Bluetooth audiostandard).

In addition, while certain embodiments make specific reference to echocancellation, a variety of audio processing techniques can becooperatively managed in the manner described herein. For example, noisereduction can be performed by accessory 204 or MCD 202; in general, oneapplication of noise reduction improves signal quality but two candegrade it. Thus, it can be helpful to coordinate noise reduction sothat it is applied exactly once. In some embodiments, the device thathas the microphone (e.g., accessory 204 as described in embodimentsabove) is selected to perform noise reduction while in duplex mode, asthe device that has the microphone is likely to provide more optimalnoise reduction. Other audio processing features such as gain controlcan also be designated to be applied by the device that has themicrophone.

In some embodiments, an accessory can explicitly indicate (e.g., duringidentification) that it is operable as a speaker phone. In otherembodiments, the mobile communication device can use any accessory as aspeaker phone, provided that accessory 204 provides a minimum set offeatures to support speaker phone operation (e.g., line-in and line-outwith duplex mode support and echo cancellation capability).

In some embodiments, circuits, processors, and/or other components of amobile communication device and/or accessory may be configured toperform various operations described herein. Those skilled in the artwill appreciate that, depending on implementation, such configurationcan be accomplished through design, setup, interconnection, and/orprogramming of the particular components and that, again depending onimplementation, a configured component might or might not bereconfigurable for a different operation. For example, a programmableprocessor can be configured by providing suitable executable code; adedicated logic circuit can be configured by suitably connecting logicgates and other circuit elements; and so on. Further, while theembodiments described above may make reference to specific hardware andsoftware components, those skilled in the art will appreciate thatdifferent combinations of hardware and/or software components may alsobe used and that particular operations described as being implemented inhardware might also be implemented in software or vice versa.

Computer programs incorporating some or all features described hereinmay be encoded on various computer readable storage media; suitablemedia include magnetic disk (including “hard” disk) or tape, opticalstorage media such as compact disk (CD) or DVD (digital versatile disk),flash memory, and the like. Computer readable storage media encoded withthe program code may be packaged with a compatible device or providedseparately from other devices. In addition, program code may be encodedand transmitted via wired optical, and/or wireless networks conformingto a variety of protocols, including the Internet, thereby allowingdistribution, e.g., via Internet download.

Thus, although the invention has been described with respect to specificembodiments, it will be appreciated that the invention is intended tocover all modifications and equivalents within the scope of thefollowing claims.

The invention claimed is:
 1. A method comprising: detecting, by amicrophone of an accessory, an input audio signal corresponding to userspeech; coordinating, between the accessory and a mobile communicationdevice (MCD) through a wireless communication channel that couples theaccessory to the MCD, which of the accessory and the MCD is to performan audio processing operation on the input audio signal detected by themicrophone of the accessory; enabling, by the accessory based oncoordinating which of the accessory and the MCD is to perform the audioprocessing operation, an audio processing operation capability, whereinthe audio processing operation capability of the MCD is disabled whilethe audio processing operation capability of the accessory is enabled;and responsive to enabling the audio processing operation capability,performing, by the accessory the audio processing operation on thedetected input audio signal.
 2. The method of claim 1 further comprisingsending, from the accessory to the MCD through the wirelesscommunication channel, capability information to indicate that theaccessory has the audio processing operation capability.
 3. The methodof claim 2, wherein the capability information is sent as part ofestablishing communication between the accessory and the MCD, andwherein the capability information indicates that the accessory has themicrophone.
 4. The method of claim 1, wherein the user speech includes arequest to initiate a phone call.
 5. The method of claim 1, wherein theaudio processing operation is an echo cancellation operation.
 6. Themethod of claim 1, wherein the audio processing operation is a noisereduction operation.
 7. An accessory for use with a mobile communicationdevice (MCD), the accessory comprising a processor and a memory havingstored therein instructions, wherein the processor upon executing theinstructions: detects, by a microphone of the accessory, an input audiosignal corresponding to user speech; coordinates with the MCD through awireless communication channel that couples the accessory to the MCD,which of the accessory and the MCD is to perform the audio processingoperation on the input audio signal detected by the microphone of theaccessory; enables, based on the coordinating, the audio processingoperation capability, wherein the audio processing operation capabilityof the MCD is disabled while the audio processing operation capabilityof the accessory is enabled; and responsive to enabling the audioprocessing operation capability, performs the audio processing operationon the detected input audio signal.
 8. The accessory of claim 7, whereinthe processor, upon executing further instructions stored in the memory,sends to the MCD through the wireless communication channel, capabilityinformation to indicate that the accessory is capable of performing theaudio processing operation, wherein the MCD is also capable ofperforming the audio processing operation.
 9. The accessory of claim 8,wherein the capability information is sent as part of establishingcommunication between the accessory and the MCD, and wherein thecapability information indicates that the accessory has the microphone.10. The accessory of claim 7, wherein the user speech includes a requestto initiate a phone call.
 11. The accessory of claim 7, wherein theaudio processing operation is an echo cancellation operation.
 12. Theaccessory of claim 7, wherein the audio processing operation is a noisereduction operation.
 13. A mobile communication device (MCD) for usewith an accessory, the MCD comprising a processor and a memory havingstored therein instructions that when executed by the processor:receives an input audio signal corresponding to user speech detected bya microphone of the accessory; coordinates with the accessory through awireless communication channel that couples the MCD to the accessory,which of the MCD and the accessory is to perform an audio processingoperation on the input audio signal detected by the microphone of theaccessory; enables, based on the coordinating, the audio processingoperation capability, wherein the audio processing operation capabilityof the accessory is disabled while the audio processing operationcapability of the MCD is enabled; and responsive to enabling the audioprocessing operation capability, performs the audio processing operationon the received input audio signal.
 14. The MCD of claim 13, wherein thereceived audio signal is detected by a microphone of the accessory. 15.The MCD of claim 13, wherein the processor, upon executing furtherinstructions stored in the memory, receives from the accessory throughthe wireless communication channel, capability information to indicatethat the accessory is capable of performing the audio processingoperation.
 16. The MCD of claim 15, wherein the capability informationis received as part of establishing communication between the MCD andthe accessory, and wherein the capability information indicates that theaccessory has the microphone.
 17. The MCD of claim 13, wherein the userspeech includes a request to initiate a phone call.
 18. The MCD of claim13, wherein the audio processing operation is an echo cancellationoperation.
 19. The MCD of claim 13, wherein the audio processingoperation is a noise reduction operation.